Transmitting data using a relay user equipment

ABSTRACT

Apparatuses, methods, and systems are disclosed for transmitting data corresponding to a relay UE. One method includes transmitting data and first information indicating relay information corresponding to retransmission of the data by a relay UE to at least one UE. The first information comprises a relay identifier, an indication that retransmission of the data is based on feedback received by the relay UE, an indication that retransmission of the data is based on a multi-hop count, an indication for the relay UE to transfer the data from a receiver buffer to a transmit buffer and to retransmit the data from the transmit buffer, an indication for the relay UE to retransmit the data to an indicated destination node, or some combination thereof. The method includes transmitting second information indicating a remaining packet delay budget to the at least one UE.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 16/517,087 filed on Jul. 19, 2019, which isincorporated herein by reference in its entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to transmitting data usinga relay user equipment.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 4^(th) Generation (“4G”), 5^(th)Generation (“5G”), 5G System (“5GS”), Positive-Acknowledgment (“ACK”),Aggregation Level (“AL”), Access and Mobility Management Function(“AMF”), Access Network (“AN”), Access Point (“AP”), AuthenticationServer Function (“AUSF”), Beam Failure Detection (“BFD”), Binary PhaseShift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report(“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Carrier Aggregation(“CA”), Contention-Based Random Access (“CBRA”), Clear ChannelAssessment (“CCA”), Control Channel Element (“CCE”), Cyclic DelayDiversity (“CDD”), Code Division Multiple Access (“CDMA”), ControlElement (“CE”), Contention-Free Random Access (“CFRA”), Closed-Loop(“CL”), Coordinated Multipoint (“CoMP”), Cyclic Prefix (“CP”), CyclicalRedundancy Check (“CRC”), Channel State Information (“CSP”), ChannelState Information-Reference Signal (“CSI-RS”), Common Search Space(“CSS”), Control Resource Set (“CORESET”), Device-to-Device (“D2D”),Discrete Fourier Transform Spread (“DFTS”), Downlink Control Information(“DCI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), DataRadio Bearer (“DRB”), Discontinuous Reception (“DRX”), Downlink PilotTime Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), EPSConnection Management (“ECM”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), Effective Isotropic Radiated Power (“EIRP”),European Telecommunications Standards Institute (“ETSI”), Evolved PacketCore (“EPC”), Evolved Packet System (“EPS”), Evolved UniversalTerrestrial Access (“E-UTRA”), Evolved Universal Terrestrial AccessNetwork (“E-UTRAN”), Frame Based Equipment (“FBE”), Frequency DivisionDuplex (“FDD”), Frequency Division Multiplexing (“FDM”), FrequencyDivision Multiple Access (“FDMA”), Frequency Division Orthogonal CoverCode (“FD-OCC”), 5G Node B or Next Generation Node B (“gNB”), GroupLeader (“GL”), General Packet Radio Services (“GPRS”), Guard Period(“GP”), Global System for Mobile Communications (“GSM”), Globally UniqueTemporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid AutomaticRepeat Request (“HARQ”), Home Location Register (“HLR”), Home PLMN(“HPLMN”), Home Subscriber Server (“HSS”), Identity or Identifier(“ID”), Information Element (“IE”), International Mobile EquipmentIdentity (“IMEI”), International Mobile Subscriber Identity (“IMSI”),International Mobile Telecommunications (“IMT”), Internet-of-Things(“IoT”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), LicensedAssisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical ChannelPrioritization (“LCP”), Log-Likelihood Ratio (“LLR”), Long TermEvolution (“LTE”), Multiple Access (“MA”), Medium Access Control(“MAC”), Multimedia Broadcast Multicast Services (“MBMS”), MinimumCommunication Range (“MCR”), Modulation Coding Scheme (“MCS”), MasterInformation Block (“MB”), Multiple Input Multiple Output (“MIMO”),Mobility Management (“MM”), Mobility Management Entity (“MME”), MobileNetwork Operator (“MNO”), massive MTC (“mMTC”), Maximum Power Reduction(“MPR”), Machine Type Communication (“MTC”), Multi User Shared Access(“MUSA”), Non Access Stratum (“NAS”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Network Entity (“NE”),Network Function (“NF”), Next Generation RAN (“NG-RAN”), Non-OrthogonalMultiple Access (“NOMA”), New Radio (“NR”), Network Repository Function(“NRF”), Network Slice Instance (“NSI”), Network Slice SelectionAssistance Information (“NSSAI”), Network Slice Selection Function(“NSSF”), Network Slice Selection Policy (“NSSP”), Operation andMaintenance System (“OAM”), Orthogonal Frequency Division Multiplexing(“OFDM”), Open-Loop (“OL”), Other System Information (“OSI”), PowerAngular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), PowerControl (“PC”), LTE-to-V2X Interface (“PC5”), Primary Cell (“PCell”),Policy Control Function (“PCF”), Physical Cell ID (“POD”), PhysicalDownlink Control Channel (“PDCCH”), Packet Data Convergence Protocol(“PDCP”), Physical Downlink Shared Channel (“PDSCH”), Pattern DivisionMultiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQIndicator Channel (“PHICH”), Power Headroom (“PH”), Power HeadroomReport (“PHR”), Physical Layer (“PHY”), Platoon Leader (“PL”), PublicLand Mobile Network (“PLMN”), Platoon Member (“PM”), Physical RandomAccess Channel (“PRACH”), Physical Resource Block (“PRB”), PrimarySecondary Cell (“PSCell”), Physical Sidelink Control Channel (“PSCCH”),Physical Uplink Control Channel (“PUCCH”), Physical Uplink SharedChannel (“PUSCH”), Quasi Co-Located (“QCL”), Quality of Service (“QoS”),Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RadioAccess Network (“RAN”), Radio Access Technology (“RAT”), Random AccessProcedure (“RACH”), Random Access Response (“RAR”), Resource ElementGroup (“REG”), Radio Link Control (“RLC”), Radio Link Monitoring(“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal(“RS”), Remaining Minimum System Information (“RMSI”), Radio ResourceControl (“RRC”), Radio Resource Management (“RRM”), Resource SpreadMultiple Access (“RSMA”), Reference Signal Received Power (“RSRP”),Round Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access(“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”),Single Carrier Frequency Division Multiple Access (“SC-FDMA”), SecondaryCell (“SCell”), Shared Channel (“SCH”), Sidelink Control Information(“SCP”), Sub-carrier Spacing (“SCS”), Service Data Unit (“SDU”), SystemInformation Block (“SIB”), SystemInformationBlockType1 (“SIB1”),SystemInformationBlockType2 (“SIB2”), Subscriber Identity/IdentificationModule (“SIM”), Signal-to-Interference-Plus-Noise Ratio (“SINR”),Sidelink (“SL”), Service Level Agreement (“SLA”), Session ManagementFunction (“SMF”), Special Cell (“SpCell”), Single Network SliceSelection Assistance Information (“S-NSSAI”), Shortened TTI (“sTTI”),Synchronization Signal (“SS”), Synchronization Signal Block (“SSB”),Scheduling UE (“SUE”), Supplementary Uplink (“SUL”), SubscriberPermanent Identifier (“SUPI”), Candidate Resource Selection Time Window(“T2”), Tracking Area (“TA”), TA Indicator (“TA1”), Transport Block(“TB”), Transport Block Size (“TBS”), Time-Division Duplex (“TDD”), TimeDivision Multiplex (“TDM”), Time Division Orthogonal Cover Code(“TD-OCC”), Transmission Power Control (“TPC”), Transmission ReceptionPoint (“TRP”), Transmission Time Interval (“TTI”), Time to Live (“TTL”),Transmit (“TX”), Uplink Control Information (“UCI”), Unified DataManagement Function (“UDM”), Unified Data Repository (“UDR”), UserEntity/Equipment (Mobile Terminal) (“UE”), Universal Integrated CircuitCard (“UICC”), Uplink (“UL”), Universal Mobile Telecommunications System(“UMTS”), User Plane (“UP”), Uplink Pilot Time Slot (“UpPTS”),Ultra-reliability and Low-latency Communications (“URLLC”), UE RouteSelection Policy (“URSP”), LTE Radio Interface (“Uu”),Vehicle-To-Everything (“V2X”), Visiting AMF (“vAMF”), Visiting NSSF(“vNSSF”), Visiting PLMN (“VPLMN”), Interconnecting Interface (“X2”)(“Xn”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, V2X communication may beused. In such networks, the V2X communication may be used to relay data.

BRIEF SUMMARY

Methods for transmitting data corresponding to a relay user equipmentare disclosed. Apparatuses and systems also perform the functions of theapparatus. One embodiment of a method includes transmitting data andfirst information indicating relay information corresponding toretransmission of the data by a relay user equipment to at least oneuser equipment. In such an embodiment, the at least one user equipmentis within a predetermine group of user equipments or outside of thepredetermined group of user equipments, the first information comprisesa relay identifier, an indication that retransmission of the data isbased on feedback received by the relay user equipment, an indicationthat retransmission of the data is based on a multi-hop count, anindication for the relay user equipment to transfer the data from areceiver buffer to a transmit buffer and to retransmit the data from thetransmit buffer, an indication for the relay user equipment toretransmit the data to an indicated destination node, or somecombination thereof. In certain embodiments, the method includestransmitting second information indicating a remaining packet delaybudget to the at least one user equipment.

One apparatus for transmitting data corresponding to a relay userequipment includes a transmitter that: transmits data and firstinformation indicating relay information corresponding to retransmissionof the data by a relay user equipment to at least one user equipment,wherein the at least one user equipment is within a predetermine groupof user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof; and transmitssecond information indicating a remaining packet delay budget to the atleast one user equipment.

One embodiment of a method for receiving data corresponding to a relayuser equipment includes receiving, by at least one user equipment, dataand first information indicating relay information corresponding toretransmission of the data by a relay user equipment. In such anembodiment, the at least one user equipment is within a predeterminegroup of user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof. In certainembodiments, the method includes receiving, by the at least one userequipment, second information indicating a remaining packet delaybudget.

One apparatus for receiving data corresponding to a relay user equipmentincludes a receiver that: receives, by at least one user equipment, dataand first information indicating relay information corresponding toretransmission of the data by a relay user equipment, wherein the atleast one user equipment is within a predetermine group of userequipments or outside of the predetermined group of user equipments, thefirst information comprises a relay identifier, an indication thatretransmission of the data is based on feedback received by the relayuser equipment, an indication that retransmission of the data is basedon a multi-hop count, an indication for the relay user equipment totransfer the data from a receiver buffer to a transmit buffer and toretransmit the data from the transmit buffer, an indication for therelay user equipment to retransmit the data to an indicated destinationnode, or some combination thereof; and receives, by the at least oneuser equipment, second information indicating a remaining packet delaybudget.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for transmitting data using a relay userequipment;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for transmitting data using a relay userequipment;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for configuring a user equipment;

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications corresponding to transmitting data using a relay userequipment;

FIG. 5 is a schematic block diagram illustrating another embodiment ofcommunications corresponding to transmitting data using a relay userequipment;

FIG. 6 is a flow chart diagram illustrating one embodiment of a methodfor transmitting data corresponding to a relay user equipment; and

FIG. 7 is a flow chart diagram illustrating one embodiment of a methodfor receiving data corresponding to a relay user equipment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 fortransmitting data using a relay user equipment. In one embodiment, thewireless communication system 100 includes remote units 102 and networkunits 104. Even though a specific number of remote units 102 and networkunits 104 are depicted in FIG. 1 , one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. The remote units 102 mayalso communicate directly with one or more of the other remote units102.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may transmit data and firstinformation indicating relay information corresponding to retransmissionof the data by a relay user equipment to at least one user equipment. Insuch an embodiment, the at least one user equipment is within apredetermine group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof. Incertain embodiments, the remote unit 102 may transmit second informationindicating a remaining packet delay budget to the at least one userequipment. Accordingly, the remote unit 102 may be used for transmittingdata corresponding to a relay user equipment.

In one embodiment, a remote unit 102 may receive, by at least one userequipment, data and first information indicating relay informationcorresponding to retransmission of the data by a relay user equipment.In such an embodiment, the at least one user equipment is within apredetermine group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof. Incertain embodiments, the remote unit 102 may receive, by the at leastone user equipment, second information indicating a remaining packetdelay budget. Accordingly, the remote unit 102 may be used for receivingdata corresponding to a relay user equipment.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used fortransmitting data using a relay user equipment. The apparatus 200includes one embodiment of the remote unit 102. Furthermore, the remoteunit 102 may include a processor 202, a memory 204, an input device 206,a display 208, a transmitter 210, and a receiver 212. In someembodiments, the input device 206 and the display 208 are combined intoa single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the transmitter 210: transmits data and firstinformation indicating relay information corresponding to retransmissionof the data by a relay user equipment to at least one user equipment,wherein the at least one user equipment is within a predetermine groupof user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof; and transmitssecond information indicating a remaining packet delay budget to the atleast one user equipment.

In various embodiments, the receiver 212: receives, by at least one userequipment, data and first information indicating relay informationcorresponding to retransmission of the data by a relay user equipment,wherein the at least one user equipment is within a predetermine groupof user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof; and receives,by the at least one user equipment, second information indicating aremaining packet delay budget.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forconfiguring a user equipment. The apparatus 300 includes one embodimentof the network unit 104. Furthermore, the network unit 104 may include aprocessor 302, a memory 304, an input device 306, a display 308, atransmitter 310, and a receiver 312. As may be appreciated, theprocessor 302, the memory 304, the input device 306, the display 308,the transmitter 310, and the receiver 312 may be substantially similarto the processor 202, the memory 204, the input device 206, the display208, the transmitter 210, and the receiver 212 of the remote unit 102,respectively.

Although only one transmitter 310 and one receiver 312 are illustrated,the network unit 104 may have any suitable number of transmitters 310and receivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

As used herein, the terms eNB and/or gNB may be used for a base station,but may be replaceable by any other radio access node (e.g., BS, eNB,gNB, AP, NR, and so forth). Furthermore, various embodiments herein maybe described in the context of 5G NR; however, the embodiments may beapplicable to other mobile communication systems supporting servingcells and/or carriers, such as systems configured for sidelinkcommunication over a PC5 interface.

In certain embodiments, for PL-to-PMs communications, a PL may transmita CAM to all the PMs including details regarding a trajectory, distancecontrol, etc., using a groupcast transmission.

In various embodiments, for PM-to-PM communications, after a CAM from aPL is received by a platoon, each PM transmits its own CAM to update thenearest platoon member using a groupcast transmission or a unicasttransmission.

In some embodiments, to enhance the reliability of message reception bymember UEs in a platoon, HARQ feedback for groupcast transmission may beused. As may be appreciated, due to vehicular shadowing or selfblocking, some member UEs may not reliably receive packets from aplatoon leader and relaying messages from the platoon leader may beperformed to enhance reliability of message reception with the group.

In certain embodiments, a platoon leader may communicate outside of agroup (e.g., platoon) to discover new platoon members and allow the newplatoon members into its group. In some embodiments, a platoon memberleaving a group may inform its platoon leader and/or other platoonmembers of its intention to leave the group. Moreover, the platoonmember may discover and/or join another platoon. In various embodiments,one platoon may merge with another platoon by creating a bigger platoongroup. In such embodiments, coverage enhancement may be achieved byrelaying messages originating from a platoon member or a platoon leader.

In some embodiments, messages are relayed or retransmitted by anintermediate UE (e.g., relay UE) based on HARQ feedback. For example, aplatoon leader transmits an initial groupcast transmission message andeach of the platoon members receives and processes the message for itsV2X application. Each platoon member then retransmits or relays themessage to its neighbor member based on HARQ feedback (e.g., based onwhether ACK is received, based on whether NACK is received, based on anACK signal strength, based on a NACK signal strength, etc.). In suchembodiments, each member UE may be provided with dedicated ACK/NACKresources and the feedback resource configuration for all UEs may beknown to each other.

In certain embodiments, messages are relayed or retransmitted byintermediate UEs without HARQ feedback. In such embodiments, a platoonleader transmits an initial groupcast transmission within or outside ofa group without expecting any HARQ feedback.

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications 400 corresponding to transmitting data using a relay userequipment (e.g., a relay based on HARQ feedback and within a group). Thecommunications 400 include messages transmitted between a TX UE 402, arelay UE 404 (e.g., intermediate UE, intermediate node), and a RX UE406. As may be appreciated, any of the communications described hereinmay include one or more messages.

In one embodiment, in a first communication 408 transmitted from the TXUE 402 to the relay UE 404 (or multiple UEs of which some or all may berelay UEs), the TX UE 402 transmits a transport block (e.g., data) withan indication for relaying the transport block by the relay UE 404(e.g., any other UE in the group, all other UEs in the group, etc.)based on HARQ feedback (e.g., within SCI).

In some embodiments, the TX UE 402 may reserve resources for the relayUE 404 to use to transmit (or retransmit) the transport block. Moreover,as part of the first communication 408 (or in another communication) theTX UE 402 may provide the reserved resource information to the relay UE404. The reserved resource information may include assistanceinformation for reserving resources, such as for periodic resourcereservation used for periodic traffic. In certain embodiments, the TX UE402 may provide the reserved resource information to the relay UE 404via a first stage or a second stage of SCI, in L1, or in L2. The relayUE 404 may use the reserved resource for retransmission based on therelay flag.

In certain embodiments, if there is no resource reservation informationtransmitted from the TX UE 402 (e.g., in SCI) to the relay UE 404, therelay UE 404 may select one or more resources for transmission (orretransmission) from a resource pool (e.g., a dedicated resource poolfor such transmissions) based on sensing which resources from theresource pool are available or by randomly selecting resources fromwithin the resource pool. In some embodiments, the resource pool may bebased on mode 2d operation. For example, mode 2d may be applied tovehicular UEs in a group. In such a scenario, only a group leader isenabled to schedule sidelink transmissions of other member UEs in thegroup. A scheduling UE may be selected by an application layer or a gNB.After the scheduling UE is selected by the application, the selectioninformation (plus group information) may be transmitted to the gNB sothat the gNB may adjust a scheduling policy for the scheduling UE. Asmay be appreciated, mode 2d may be applicable for groupcast and unicastservices. For in-coverage embodiments, the scheduling UE may beconfigured by a base station. While for out-of-coverage embodiments, thescheduling UE may be pre-configured as the scheduling UE. For example, aUE with high capability or scheduling capability may be appointed as thescheduling UE. For groupcast services, the leader UE in the group (e.g.,the head vehicle in a platoon) may manage the group.

In certain embodiments, in the first communication 408 transmitted fromthe TX UE 402 to the relay UE 404 (or multiple UEs of which some or allmay be relay UEs), the TX UE 402 transmits end to end latencyinformation to the relay UE 404 for the relay UE 404 to use fordelivering the transport block. The end to end latency information maybe conveyed by transmitting a remaining packet delay budget (e.g., a TTLconfiguration for transport block reception).

In some embodiments, SCI (e.g., SCI fields) or other signaling may beused to transmit the following information from the TX UE 402 to therelay UE 404: 1) end to end latency information; 2) resource reservationinformation for the relay UE 404 to use for transmitting orretransmitting data (e.g., a transport block) (for example, this may beincluded in the first stage or the second stage of the SCI); and/or 3) arelay flag that indicates whether a groupcast transport block that isreceived with a destination group ID should be transmitted orretransmitted by the relay UE 404 (e.g., based on HARQ feedback). Incertain embodiments, a relay flag may be an L2 or L3 flag present in MACCE, RLC, or PDCP headers instead of being part of SCI.

In various embodiments, one or more relay UEs 404 may be selected fortransmission (or retransmission) of the transport block received fromthe TX UE 402. The selection of the one or more relay UEs 404 may be aselection of one or more UEs within a group (e.g., platoon) configuredto receive and process HARQ feedback information from all member UEs inthe group. The selection may be based on one of the followingoptions: 1) the gNB may configure (e.g., semi-statically, statically,dynamically, etc.) an SUE in the group that monitors the HARQ NACKfeedback within the group and transmits (or retransmits) the transportblock in response to receiving HARQ NACK feedback (there may be one ormore SUEs in a group and the UE ID of the one or more SUEs may be knownto the group member UEs); 2) the selection of one or more relay UEs 404for transmission (or retransmission) may be dynamically determined bythe UEs in a group based on a HARQ NACK feedback and/or a HARQ ACKfeedback reception threshold (e.g., signal strength) (the threshold maybe an RSRP or SINR threshold configured by the gNB or by the TX UE402—for example, any UE in the group that receives HARQ NACK feedbackhaving a signal strength above a certain threshold may act as a relay UE404 and may transmit (or retransmit) the transport block within thegroup); 3) the selection of one or more relay UEs 404 may be dynamicallydetermined by a group member UE based on HARQ ACK feedback, HARQ NACKfeedback, and/or explicit signaling (e.g., in one example a group memberUE may not decode an initial groupcast transport block and all group UEsmay monitor a HARQ ACK feedback resource of surrounding member UEs— bynot receiving a HARQ ACK from a nearby UE a group member UE may knowthat it needs to transmit or retransmit the transport block, in anotherexample, a UE that does not receive the initial groupcast transportblock may explicitly signal the need for transmission orretransmission—a group member UE that is near that UE may act as a relayUE 404 based on the received signal strength of the HARQ ACK message. Inone embodiment, the explicit signaling may include L1 SCI signaling witha relay request flag.); and/or 4) all group member UEs or a subset ofgroup member UEs may be used for transmission, retransmission, and/orrelay (e.g., based on reception of HARQ ACK and/or HARQ NACK feedback).

In some embodiments, the relay UE 404 within the group may receive theinitial transport block from the TX UE 402 may monitor for a thirdcommunication 412 that includes HARQ feedback and/or signalingtransmitted from the RX UE 406 (e.g., a group member UE) to the relay UE404.

The relay UE 404 may determine 414 whether it should retransmit thetransport block to the RX UE 406 based on: whether the relay UE 404 isselected for retransmission; whether a HARQ ACK and/or HARQ NACK wasreceived; a signal strength of a received HARQ ACK; a signal strength ofa received HARQ NACK; and/or an explicit signal indicatingretransmission.

In response to the relay UE 404 determining 414 to retransmit thetransport block, in a fourth communication 416, the relay UE 404retransmits the transport block to the RX UE 406.

In various embodiments, the relay UE 404 takes into account theremaining packet delay budget value transmitted by the TX UE 402 toschedule a transmission or retransmission. In one embodiment, the delaybudget value may be used as a T2 value (e.g., a number of subframes orslots expressed in ms) for candidate resource selection.

In some embodiments, the relay UE 404 may, based on a relay flag (e.g.,a relay flag in SCI, an L1 relay flag, an L2 relay flag, an L3 relayflag, etc.), transfer a transport block (e.g., data) from a receivebuffer to a transmit buffer for transmission or retransmission (e.g., inthe fourth communication 416). In such embodiments, the relay UE 404 maychoose to transmit the transport block with the same HARQ process IDused by the TX UE 402, or the relay UE 404 may signal the HARQ processID used by the TX UE 402 separately in SCI and may signal a redundancyversion (e.g., for use in soft combining). In various embodiments, therelay UE 404 may check a destination group ID corresponding to atransport block and determine whether the message is for itself and/orfor transmission or retransmission (e.g., based on a relay flag and/orHARQ feedback).

In certain embodiments, the relay UE 404 may have a configured maximumHARQ retransmission counter that it uses for transport blocks that donot originate from the relay UE 404 to count a number of times that thetransport block is retransmitted by the relay UE 404.

In various embodiments, in a fifth communication 418 transmitted fromthe relay UE 404 to the TX UE 402, the relay UE 404 may transmit astatus of groupcast message delivery (e.g., status of transmission orretransmission by the relay UE 404) to the TX UE 402. In suchembodiments, feedback timing and resources may be provided by the TX UE402 to the relay UE 404 so that the status of the groupcast messagedelivery may be sent to the TX UE 402. In embodiments corresponding toNR mode 1 in which the gNB schedules the sidelink transmission of therelay UE 404, downlink control information or a semi-staticconfiguration contains an additional information element about a beamsweeping configuration that includes a time, frequency, spatialdirection, and/or selection of antenna panel for the relay UE 404 forthe groupcast or unicast control channel and data channel transmission.In embodiments corresponding to UE to UE relaying, the TX UE 402configures the relay UE 404 either with sidelink control information ora semi-static configuration about the beam sweeping configuration thatincludes the time, frequency, spatial direction, and/or selection ofantenna panel for the relay UE 404 for the groupcast or unicast controlchannel and data channel transmission.

FIG. 5 is a schematic block diagram illustrating another embodiment ofcommunications 500 corresponding to transmitting data using a relay userequipment (e.g., a relay based on a blind hop with no HARQfeedback—within or outside of a group). The communications 500 includemessages transmitted between a TX UE 502, a relay UE 504 (e.g.,intermediate UE), and a RX UE 506. As may be appreciated, any of thecommunications described herein may include one or more messages.

In one embodiment, in a first communication 508 transmitted from the TXUE 502 (or another relay UE) to the relay UE 504 (or multiple UEs ofwhich some or all may be relay UEs), the TX UE 502 transmits a transportblock (e.g., data) with an indication for relaying the transport blockby the relay UE 504 (e.g., any other UE in the group, all other UEs inthe group, etc.) without waiting for any HARQ feedback and including arequired hop count for the transport block delivery (e.g., in SCI).

In some embodiments, the TX UE 502 may reserve resources for the relayUE 504 to use to transmit (or retransmit) the transport block. Moreover,as part of the first communication 508 (or in another communication) theTX UE 502 may provide the reserved resource information to the relay UE504. The reserved resource information may include assistanceinformation for reserving resources, such as for periodic resourcereservation used for periodic traffic. In certain embodiments, the TX UE502 may provide the reserved resource information to the relay UE 504via a first stage or a second stage of SCI, in L1, or in L2.

In certain embodiments, if there is no resource reservation informationtransmitted from the TX UE 502 (e.g., in SCI) to the relay UE 504, therelay UE 504 may select one or more resources for transmission (orretransmission) from a resource pool (e.g., a dedicated resource poolfor such transmissions) based on sensing which resources from theresource pool are available or by randomly selecting resources fromwithin the resource pool. In some embodiments, the resource pool may bebased on mode 2d operation.

In certain embodiments, in the first communication 508 transmitted fromthe TX UE 502 to the relay UE 504 (or multiple UEs of which some or allmay be relay UEs), the TX UE 502 (or another relay UE) transmits end toend latency information to the relay UE 504 for the relay UE 504 to usefor delivering the transport block. The end to end latency informationmay be conveyed by transmitting a remaining packet delay budget (e.g., aTTL configuration for transport block reception).

In some embodiments, SCI (e.g., SCI fields) or other signaling may beused to transmit the following information from the TX UE 502 to therelay UE 504: 1) end to end latency information; 2) resource reservationinformation for the relay UE 504 to use for transmitting orretransmitting data (e.g., a transport block) (for example, this may beincluded in the first stage or the second stage of the SCI); 3) adirection of the data to be relayed, such as information indicating zoneIDs (e.g., IDs corresponding to a zone of UEs), a direction to transmitdata, and/or a communication range (e.g., MCR); and/or 4) a remaininghop count, remaining packet delay budget, a destination group ID, adestination node ID, and/or a relay node ID. As may be appreciated, azone ID may be an identifier that corresponds to a geographic area orzone.

In various embodiments, one or more relay UEs 504 may be selected fortransmission (or retransmission) of the transport block received fromthe TX UE 502. The selection of the one or more relay UEs 504 may be aselection of one or more UEs within a group (e.g., platoon). Theselection may be based on one of the following options: 1) a UE withinthe group; 2) a UE outside of the group; 3) relay node IDs (e.g.,transmitted in DCI by the gNB such as part of gNB assisted sidelinkscheduling, an L1 relay ID, an L2 relay ID, etc.); 4); a direction, ageolocation, a zone ID, and/or an MCR; 5) a gNB, a group leader UE, or aSUE may configure (e.g., semi-statically, statically, dynamically, etc.)one or more relay UEs 504 that transmit (or retransmit) the transportblock; and/or 6) all group member UEs or a subset of group member UEsmay be used for transmission, retransmission, and/or relay. In certainembodiments, such as for NR Mode 1 scheduling, the TX UE 402, as part ofUE assistance information, may provide information such as direction,geolocation, zone ID, and/or MCR to the gNB.

In various embodiments, an L1 or L2 destination ID field may be set asfollows: 1) if a groupcast message (e.g., data, transport block) needsto be relayed inside the same group (e.g., blindly), then thedestination group ID should be set to the group ID for which thegroupcast message was sent; 2) if a unicast message needs to be relayedinside the group or outside the group, then the destination node ID andthe relay node ID should be set so that a relay UE 504 (having the relaynode ID) relays the message based on the destination node ID; 3) therelay UE 504 may implicitly understand from a destination group ID and aremaining hop count (value >0) that a message is to be transmitted orretransmitted to a group having the destination group ID— therefore therelay UE 504 transfers the received data from its RX buffer to its TXbuffer and transmits or retransmits the message to the group having thedestination group ID; and/or 4) the relay UE 504 (having the relay nodeID) may implicitly understand from a destination node ID and a relaynode ID that a message not for itself is to be transmitted orretransmitted—therefore, the relay UE 504 transfer the received datafrom the RX buffer to the TX buffer for transmission to the destinationnode ID.

The relay UE 504 determines 512 whether to retransmit the transportblock received from the TX UE 502 (or another relay UE). To make thisdetermination, the relay UE 504 takes into account assistanceinformation received from the TX UE 502 (or another relay UE), such asremaining hop count and a remaining packet delay budget.

In response to the relay UE 504 determining 512 to retransmit thetransport block, in a third communication 514, the relay UE 504retransmits the transport block to the RX UE 506.

In certain embodiments, for a groupcast transmission of a message, therelay UE 504 processes the message, then, with information such as adestination group ID and a remaining hop count, transmits or retransmitsthe message by transferring the message from its RX buffer to its TXbuffer.

In various embodiments, for a unicast transmission of a message, therelay UE 504 receives the message using a relay ID, does not process themessage for itself, then, with information such as destination node IDand relay ID, transfers the message to its TX buffer for transmitting orretransmitting the message using the destination node ID.

In some embodiments, the relay UE 504 checks a zone ID, an MCR, and/or aremaining hop count before transmitting or retransmitting a message tomake sure that the message should be transmitted or retransmitted and totransmit the message to correct UEs. For example, if the remaining hopcount is greater than zero, the message should be transmitted orretransmitted. In certain embodiments, the relay UE 504 adjusts the zoneID, the MCR, and/or the remaining hop count and includes the adjustedzone ID, the adjusted MCR, and/or the adjusted remaining hop count withthe message that is transmitted and/or retransmitted.

FIG. 6 is a flow chart diagram illustrating one embodiment of a method600 for transmitting data corresponding to a relay user equipment. Insome embodiments, the method 600 is performed by an apparatus, such asthe remote unit 102. In certain embodiments, the method 600 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 600 may include transmitting 602 data and first informationindicating relay information corresponding to retransmission of the databy a relay user equipment to at least one user equipment. In such anembodiment, the at least one user equipment is within a predeterminegroup of user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof. In certainembodiments, the method 600 includes transmitting 604 second informationindicating a remaining packet delay budget to the at least one userequipment.

In certain embodiments, the data comprises a transport block. In someembodiments, the second information is part of scheduling assistanceinformation. In various embodiments, the first information and thesecond information are part of sidelink control information. In certainembodiments, the first information and the second information may betransmitted together for a single stage SCI or separately for two stageSCI.

In one embodiment, the at least one user equipment is selected based ona scheduling user equipment. In certain embodiments, the at least oneuser equipment is selected based on a negative feedback signal strength,a positive feedback signal strength, a signal indicating retransmission,or some combination thereof. In some embodiments, the at least one userequipment is selected based on a geolocation, a direction, a zone, aconfiguration, or some combination thereof.

In various embodiments, the method 600 further comprises transmittingthird information indicating resource reservation information for the atleast one user equipment to retransmit the data, wherein the resourcereservation information comprises periodic resource reservationinformation. In one embodiment, the method 600 further comprisestransmitting scheduling assistance information comprising user equipmentassistance information indicating a traffic arrival rate for periodictraffic. In certain embodiments, the method 600 further comprisestransmitting third information comprising a destination groupidentifier, wherein the third information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof.

In some embodiments, the first information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof. In various embodiments, themethod 600 further comprises transmitting third information comprisingzones corresponding to the data, a minimum communication range, aremaining hop count, or some combination thereof.

FIG. 7 is a flow chart diagram illustrating one embodiment of a method700 for receiving data corresponding to a relay user equipment. In someembodiments, the method 700 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 700 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 700 may include receiving 702, by at least one userequipment, data and first information indicating relay informationcorresponding to retransmission of the data by a relay user equipment.In such an embodiment, the at least one user equipment is within apredetermine group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof. Incertain embodiments, the method 700 includes receiving 704, by the atleast one user equipment, second information indicating a remainingpacket delay budget.

In certain embodiments, the data comprises a transport block. In someembodiments, the second information is part of scheduling assistanceinformation. In various embodiments, the first information and thesecond information are part of sidelink control information. In certainembodiments, the first information and the second information may betransmitted together for a single stage SCI or separately for two stageSCI.

In one embodiment, the at least one user equipment is selected based ona scheduling user equipment. In certain embodiments, the at least oneuser equipment is selected based on a negative feedback signal strength,a positive feedback signal strength, a signal indicating retransmission,or some combination thereof. In some embodiments, the at least one userequipment is selected based on a geolocation, a direction, a zone, aconfiguration, or some combination thereof.

In various embodiments, the method 700 further comprises receiving thirdinformation indicating resource reservation information for the at leastone user equipment to retransmit the data, wherein the resourcereservation information comprises periodic resource reservationinformation. In one embodiment, the method 700 further comprisesreceiving scheduling assistance information comprising user equipmentassistance information indicating a traffic arrival rate for periodictraffic. In certain embodiments, the method 700 further comprisesreceiving third information comprising a destination group identifier,wherein the third information is used to determine whether the data isto be processed internally, whether the data is to be retransmitted, ora combination thereof.

In some embodiments, the first information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof. In various embodiments, themethod 700 further comprises receiving third information comprisingzones corresponding to the data, a minimum communication range, aremaining hop count, or some combination thereof.

In one embodiment, a method comprises: transmitting data and firstinformation indicating relay information corresponding to retransmissionof the data by a relay user equipment to at least one user equipment,wherein the at least one user equipment is within a predetermine groupof user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof; andtransmitting second information indicating a remaining packet delaybudget to the at least one user equipment.

In certain embodiments, the data comprises a transport block.

In some embodiments, the second information is part of schedulingassistance information.

In various embodiments, the first information and the second informationare part of sidelink control information. In certain embodiments, thefirst information and the second information may be transmitted togetherfor a single stage SCI or separately for two stage SCI.

In one embodiment, the at least one user equipment is selected based ona scheduling user equipment.

In certain embodiments, the at least one user equipment is selectedbased on a negative feedback signal strength, a positive feedback signalstrength, a signal indicating retransmission, or some combinationthereof.

In some embodiments, the at least one user equipment is selected basedon a geolocation, a direction, a zone, a configuration, or somecombination thereof.

In various embodiments, the method further comprises transmitting thirdinformation indicating resource reservation information for the at leastone user equipment to retransmit the data, wherein the resourcereservation information comprises periodic resource reservationinformation.

In one embodiment, the method further comprises transmitting schedulingassistance information comprising user equipment assistance informationindicating a traffic arrival rate for periodic traffic.

In certain embodiments, the method further comprises transmitting thirdinformation comprising a destination group identifier, wherein the thirdinformation is used to determine whether the data is to be processedinternally, whether the data is to be retransmitted, or a combinationthereof.

In some embodiments, the first information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof.

In various embodiments, the method further comprises transmitting thirdinformation comprising zones corresponding to the data, a minimumcommunication range, a remaining hop count, or some combination thereof.

In one embodiment, an apparatus comprises: a transmitter that: transmitsdata and first information indicating relay information corresponding toretransmission of the data by a relay user equipment to at least oneuser equipment, wherein the at least one user equipment is within apredetermine group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof andtransmits second information indicating a remaining packet delay budgetto the at least one user equipment.

In certain embodiments, the data comprises a transport block.

In some embodiments, the second information is part of schedulingassistance information.

In various embodiments, the first information and the second informationare part of sidelink control information. In certain embodiments, thefirst information and the second information may be transmitted togetherfor a single stage SCI or separately for two stage SCI.

In one embodiment, the at least one user equipment is selected based ona scheduling user equipment.

In certain embodiments, the at least one user equipment is selectedbased on a negative feedback signal strength, a positive feedback signalstrength, a signal indicating retransmission, or some combinationthereof.

In some embodiments, the at least one user equipment is selected basedon a geolocation, a direction, a zone, a configuration, or somecombination thereof.

In various embodiments, the transmitter transmits third informationindicating resource reservation information for the at least one userequipment to retransmit the data, and the resource reservationinformation comprises periodic resource reservation information.

In one embodiment, the transmitter transmits scheduling assistanceinformation comprising user equipment assistance information indicatinga traffic arrival rate for periodic traffic.

In certain embodiments, the transmitter transmits third informationcomprising a destination group identifier, and the third information isused to determine whether the data is to be processed internally,whether the data is to be retransmitted, or a combination thereof.

In some embodiments, the first information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof.

In various embodiments, the transmitter transmits third informationcomprising zones corresponding to the data, a minimum communicationrange, a remaining hop count, or some combination thereof.

In one embodiment, a method comprises: receiving, by at least one userequipment, data and first information indicating relay informationcorresponding to retransmission of the data by a relay user equipment,wherein the at least one user equipment is within a predetermine groupof user equipments or outside of the predetermined group of userequipments, the first information comprises a relay identifier, anindication that retransmission of the data is based on feedback receivedby the relay user equipment, an indication that retransmission of thedata is based on a multi-hop count, an indication for the relay userequipment to transfer the data from a receiver buffer to a transmitbuffer and to retransmit the data from the transmit buffer, anindication for the relay user equipment to retransmit the data to anindicated destination node, or some combination thereof; and receiving,by the at least one user equipment, second information indicating aremaining packet delay budget.

In certain embodiments, the data comprises a transport block.

In some embodiments, the second information is part of schedulingassistance information.

In various embodiments, the first information and the second informationare part of sidelink control information. In certain embodiments, thefirst information and the second information may be transmitted togetherfor a single stage SCI or separately for two stage SCI.

In one embodiment, the at least one user equipment is selected based ona scheduling user equipment.

In certain embodiments, the at least one user equipment is selectedbased on a negative feedback signal strength, a positive feedback signalstrength, a signal indicating retransmission, or some combinationthereof.

In some embodiments, the at least one user equipment is selected basedon a geolocation, a direction, a zone, a configuration, or somecombination thereof.

In various embodiments, the method further comprises receiving thirdinformation indicating resource reservation information for the at leastone user equipment to retransmit the data, wherein the resourcereservation information comprises periodic resource reservationinformation.

In one embodiment, the method further comprises receiving schedulingassistance information comprising user equipment assistance informationindicating a traffic arrival rate for periodic traffic.

In certain embodiments, the method further comprises receiving thirdinformation comprising a destination group identifier, wherein the thirdinformation is used to determine whether the data is to be processedinternally, whether the data is to be retransmitted, or a combinationthereof.

In some embodiments, the first information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof.

In various embodiments, the method further comprises receiving thirdinformation comprising zones corresponding to the data, a minimumcommunication range, a remaining hop count, or some combination thereof.

In one embodiment, an apparatus comprises: a receiver that: receives, byat least one user equipment, data and first information indicating relayinformation corresponding to retransmission of the data by a relay userequipment, wherein the at least one user equipment is within apredetermine group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof; andreceives, by the at least one user equipment, second informationindicating a remaining packet delay budget.

In certain embodiments, the data comprises a transport block.

In some embodiments, the second information is part of schedulingassistance information.

In various embodiments, the first information and the second informationare part of sidelink control information. In certain embodiments, thefirst information and the second information may be transmitted togetherfor a single stage SCI or separately for two stage SCI.

In one embodiment, the at least one user equipment is selected based ona scheduling user equipment.

In certain embodiments, the at least one user equipment is selectedbased on a negative feedback signal strength, a positive feedback signalstrength, a signal indicating retransmission, or some combinationthereof.

In some embodiments, the at least one user equipment is selected basedon a geolocation, a direction, a zone, a configuration, or somecombination thereof.

In various embodiments, the receiver receives third informationindicating resource reservation information for the at least one userequipment to retransmit the data, and the resource reservationinformation comprises periodic resource reservation information.

In one embodiment, the receiver receives scheduling assistanceinformation comprising user equipment assistance information indicatinga traffic arrival rate for periodic traffic.

In certain embodiments, the receiver receives third informationcomprising a destination group identifier, and the third information isused to determine whether the data is to be processed internally,whether the data is to be retransmitted, or a combination thereof.

In some embodiments, the first information is used to determine whetherthe data is to be processed internally, whether the data is to beretransmitted, or a combination thereof.

In various embodiments, the receiver receives third informationcomprising zones corresponding to the data, a minimum communicationrange, a remaining hop count, or some combination thereof.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. A method comprising: receiving, by at leastone user equipment, data and first information indicating relayinformation corresponding to retransmission of the data by a relay userequipment, wherein the at least one user equipment is within apredetermined group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof; andreceiving, by the at least one user equipment, second informationindicating a remaining packet delay budget, wherein the at least oneuser equipment uses the first information and the remaining packet delaybudget for scheduling retransmission of the data.
 2. The method of claim1, wherein the remaining packet delay budget comprises a time to liveconfiguration for packet reception.
 3. The method of claim 1, whereinthe first information comprises a relay flag.
 4. The method of claim 1,further comprising receiving feedback resource and timing information tocarry feedback corresponding to a data transmission.
 5. An apparatuscomprising: a receiver that: receives, by the apparatus, data and firstinformation indicating relay information corresponding to retransmissionof the data by a relay user equipment, wherein the apparatus is within apredetermined group of user equipments or outside of the predeterminedgroup of user equipments, the first information comprises a relayidentifier, an indication that retransmission of the data is based onfeedback received by the relay user equipment, an indication thatretransmission of the data is based on a multi-hop count, an indicationfor the relay user equipment to transfer the data from a receiver bufferto a transmit buffer and to retransmit the data from the transmitbuffer, an indication for the relay user equipment to retransmit thedata to an indicated destination node, or some combination thereof; andreceives, by the apparatus, second information indicating a remainingpacket delay budget, wherein the apparatus uses the first informationand the remaining packet delay budget for scheduling retransmission ofthe data.
 6. The apparatus of claim 5, wherein the remaining packetdelay budget comprises a time to live configuration for packetreception.
 7. The apparatus of claim 5, wherein the first informationcomprises a relay flag.
 8. The apparatus of claim 5, wherein thereceiver receives feedback resource and timing information to carryfeedback corresponding to a data transmission.